Methods and apparatus to facilitate voicemail interaction

ABSTRACT

Example methods and apparatus to facilitate voicemail interaction are disclosed. A disclosed example method involves, during a call session with a voicemail system, receiving an audio segment from the voicemail system. The example method also involves performing feature recognition on the audio segment and outputting a display element to a user interface based on a recognized feature in the audio segment.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to communication devices and,more particularly, to methods and apparatus to facilitate voicemailinteraction.

BACKGROUND

Voicemail systems enable users to receive voicemail messages at a remotevoicemail system location and retrieve those voicemail messages via oneor more devices. That is, if a person is unable or unwilling to answer atelephone call, a voicemail system enables the telephone call to beanswered by a voicemail service that permits a calling party to leave avoicemail message for the person or the called party. Subsequently, thecalled party may contact the voicemail service to access a correspondingvoicemail account and listen to the voicemail message left by thecalling party. Voicemail systems are often implemented using interactivevoice response (IVR) systems in which users listen to instructions fornavigating through the voicemail systems.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an example voicemail call session in which a user deviceis in communication with an interactive voice response (IVR) voicemailsystem.

FIG. 2 depicts the example user device of FIG. 1 displaying user controlprompts based on information received from the IVR voicemail system ofFIG. 1.

FIG. 3 depicts the example user device of FIG. 1 displaying a visualnotification based on information received from the IVR voicemail systemof FIG. 1.

FIG. 4 depicts an example audio segment transmitting a speech signal onwhich speech recognition may be performed.

FIG. 5 depicts an example audio segment having a human-perceptible audioportion and a human-imperceptible affixed information portion.

FIG. 6 depicts an example audio segment having a human-perceptible audioportion and human-imperceptible embedded information.

FIG. 7 depicts an example apparatus that may be used to facilitatevoicemail interactions by detecting features in transmissions from theIVR voicemail system of FIG. 1.

FIG. 8 depicts an example block diagram of a mobile device that may beused to implement an example user device of FIGS. 1-3 and/or the exampleapparatus of FIG. 7.

FIG. 9 depicts an example flow diagram representative of computerreadable instructions that may be used to facilitate voicemailinteractions based on detecting features in transmissions from the IVRvoicemail system of FIG. 1.

FIG. 10 depicts an example flow diagram representative ofcomputer-readable instructions that may be used to perform speechrecognition on audio segments in connection with the example flowdiagram of FIG. 9.

FIG. 11 depicts an example flow diagram representative ofcomputer-readable instructions that may be used to retrieve informationfrom human-imperceptible affixed signals in audio segments in connectionwith the example flow diagram of FIG. 9.

FIG. 12 depicts an example flow diagram representative ofcomputer-readable instructions that may be used to retrieve embeddedinformation from audio segments in connection with the example flowdiagram of FIG. 9.

DETAILED DESCRIPTION

Although the following discloses example methods, apparatus, andarticles of manufacture including, among other components, softwareexecuted on hardware, it should be noted that such methods, apparatus,and articles of manufacture are merely illustrative and should not beconsidered as limiting. For example, it is contemplated that any or allof these hardware and software components could be embodied exclusivelyin hardware, exclusively in software, exclusively in firmware, or in anycombination of hardware, software, and/or firmware. Accordingly, whilethe following describes example methods, apparatus, and articles ofmanufacture, persons having ordinary skill in the art will readilyappreciate that the examples provided are not the only way to implementsuch methods, apparatus, and articles of manufacture.

It will be appreciated that, for simplicity and clarity of illustration,where considered appropriate, reference numerals may be repeated amongthe figures to indicate corresponding or analogous elements. Inaddition, numerous specific details are set forth in order to provide athorough understanding of examples disclosed herein. However, it will beunderstood by those of ordinary skill in the art that examples disclosedherein may be practiced without these specific details. In otherinstances, well-known methods, procedures and components have not beendescribed in detail so as not to obscure examples disclosed herein.Also, the description is not to be considered as limiting the scope ofexamples disclosed herein.

Example methods, apparatus, and articles of manufacture disclosed hereinmay be used in connection with telephony-capable mobile devices, whichmay be any mobile communication device, mobile computing device, or anyother element, entity, device, or service capable of communicatingwirelessly. Mobile devices, also referred to as terminals, wirelessterminals, mobile stations, communication stations, user equipment (UE),or user devices, may include mobile smart phones (e.g., BlackBerry®smart phones), cellular telephones, wireless personal digital assistants(PDA), tablet/laptop/notebook/netbook computers with wireless adapters,etc.

In some examples, disclosed example methods, apparatus, and articles ofmanufacture may be implemented in connection with other types oftelecommunication devices such as plain old telephone service(POTS)-based landline telephones, voice over internet protocol (VoIP)telephones, etc.

Traditional IVR voicemail system interactions involve prompts,notifications, and/or confirmations that are sent to users via audioonly, requiring that a user device (e.g., a telephone) be held to aperson's ear, be in speaker-phone mode, or be attached to a headset wornby a user of the device. When the user device is not in speaker-phonemode or is not attached to a headset worn by a user of the device, theuser must put the user device to his/her ear to listen to audio prompts,move the user device away from his/her ear to press a key for a desiredaction (e.g., delete, save, forward, send, skip, create, etc. avoicemail message), and move the user device back to his/her ear tolisten for an audio notification or confirmation that the desired actionhas occurred. Such back and forth movement between a user's ear and theuser's view of the user device can be time consuming, tedious, andcumbersome when navigating a voicemail call session. For example, suchback and forth movement introduces discontinuities in a user's visualfocus on a user device keypad or touch-screen display such that eachtime a user moves the user device back into viewing position, the usermust refocus and re-orient his/her sight on the user device keypad ortouch-screen display. Similarly, each time the user moves the userdevice back to his/her ear, the user must re-position the device foroptimal comfort and hearing.

Another drawback of traditional IVR voicemail system interactions is thesignificant reliance on a user's ability to hear audio information(e.g., prompts, notifications, confirmations, etc.) and also remembersuch audio information during a voicemail call session. For example, ifa user is in a voicemail call session while in a noisy environment, theuser may not be able to correctly hear all voicemail system prompts ormay be distracted such that the user becomes confused as to which keysto press for different features or operations (e.g., delete, save,forward, send, skip, create, etc. a voicemail message). This can beparticularly frustrating and potentially risky if a person confuses anumeric key for a delete operation with a numeric key for a saveoperation. In such an instance, if the person intends to save animportant voicemail message, the person may inadvertently delete thevoicemail message by pressing the numeric key corresponding to a deleteoperation when the person mistakenly thought it corresponded to a saveoperation. In addition, if the person does not move the user device backto his/her ear or does move the user device back to his/her ear but isin a noisy environment, the person may not hear the audio confirmationthat the message has been deleted rather than saved.

Example methods, apparatus, and articles of manufacture disclosed hereinfacilitate voicemail interactions between users and interactive voiceresponse (IVR) voicemail systems during voicemail call sessions in whichusers listen to voicemail messages from other persons or create/sendvoicemail messages to other persons. In particular, unlike traditionalIVR voicemail system interactions in which users are informed ofprompts, notifications, and/or confirmations via audio only and in whicha user device must be held to a person's ear, must be in speaker-phonemode, or must be attached to a headset worn by the person, examplesdisclosed herein enable conducting voicemail system interactions usingvisual information displayed on a user device (e.g., a mobile telephone,a landline telephone, a VoIP telephone, etc.). Such visual informationmay be visual cues such as user interface input/control prompts (e.g., adelete message control, a save message control, a forward messagecontrol, a send message control, a skip message control, etc.) and/ornotifications such as confirmations of completed user requests (e.g.,confirmations of deleted messages, saved messages, forwarded messages,sent messages, skipped messages, etc.), requests for user-initiation ofuser-requested operations (e.g., confirm user-selection to initiatemessage deletion, confirm user-selection to initiate saving of message,confirm user-selection to initiate forwarding of message, confirmuser-selection to initiate skipping of message, confirm user-selectionto initiate ending of voicemail session, etc.), and voicemail accountstatus information (e.g., a quantity of new messages, a quantity ofsaved messages, a quantity of storage space remaining, etc.).

A disclosed example method to facilitate voicemail interaction involves,during a call session with a voicemail system, receiving an audiosegment from the voicemail system. A feature recognition operation isthen performed on the audio segment and a display element or displayinformation is output to a user interface of a user device (e.g., amobile telephone, a landline telephone, a VoIP telephone, etc.) fordisplay based on a recognized feature in the audio segment.

In some examples, during a voicemail call session, a connected userdevice displays visual information based on device-recognizableinformation or features received in audio communications from avoicemail system. For example, such device-recognizable information maybe human-perceptible automated voice-recorded prompts that are sent byIVR voicemail systems and are speech-recognizable by receiving userdevices. Additionally or alternatively, audio communications sent byvoicemail systems in accordance with examples disclosed herein mayinclude affixed information that is imperceptible or substantiallyimperceptible to humans. Such human-imperceptible affixed informationmay be affixed to the beginning (e.g., pre-fixed information), themiddle (e.g., infixed information), the end (e.g., suffixed orpost-fixed information), the beginning and end (e.g., circumfixedinformation), and/or interleaved through one or more portions (e.g.,transfixed information) of human-perceptible audio and are structured,configured, or otherwise intended to be recognizable by receivingdevices to trigger, prompt, or otherwise cause the receiving devices todisplay corresponding information. Additionally or alternatively, audiocommunications sent by voicemail systems in accordance with examplesdisclosed herein may include embedded information that is imperceptibleor substantially imperceptible to humans. Such human-imperceptibleembedded information may be embedded in human-perceptible audio and isstructured, configured, or otherwise intended to be recognizable byreceiving devices to trigger, prompt, or otherwise cause the receivingdevices to display corresponding information. In other examples, othertechniques may be used to cause receiving devices to display voicemailinteraction information for viewing by users while interacting withvoicemail systems during voicemail call sessions.

FIG. 1 depicts an example voicemail call session 100 in which a userdevice 102 is in communication with an IVR voicemail system 104. Theuser device 102 of the illustrated example is a mobile telephone.However, the user device 102 may be implemented using any other type ofuser device as discussed above. In the illustrated example, the userdevice 102 is connected to the IVR voicemail system 104 via a callsession connection 106. The call session connection 106 of theillustrated example is a voice connection or a connection suitable forexchanging voice communications and may be established using anysuitable type of telecommunication connection including, for example, apacket switched connection or a circuit switched connection. Inaddition, the call session connection 106 may be implemented using aPOTS connection, a wireless cellular connection, a VoIP connection, apublic switched telephone network (PSTN) connection, a public landmobile network (PLMN) connection, and/or any other type of connection,and/or any combination thereof.

In the illustrated example, the IVR voicemail system 104 includes or isconnected to one or more databases or data stores, one of which is shownas an example voicemail system data store 108. The example voicemailsystem data store 108 stores pre-recorded IVR voice prompts, voicenotifications, voice confirmations, voice status information, etc. thatare communicated to user devices during voicemail call sessions toenable users to interact with the IVR voicemail system 104. In addition,the voicemail system data store 108 also stores voicemail messages fordifferent user accounts.

The IVR voicemail system 104 of the illustrated example communicateswith the user device 102 using audio communications. In the illustratedexample, the IVR voicemail system 104 is shown sending an IVR audiosegment 110 to the user device 102 via the call session connection 106,and the user device 102 is shown sending a user input audio segment 112to the IVR voicemail system 104 via the call session connection 106. TheIVR audio segment 110 may communicate a user prompt soliciting userinput, a notification, a confirmation, voicemail account statusinformation, etc. In the illustrated example, a user prompt solicitinguser input may be an automated voice prompt informing a user ofnumerical keys to press for different operations such as ‘listen to amessage’, ‘delete a message’, ‘save a message’, ‘forward a message’,‘send a message’, ‘skip a message’, ‘create a message’, etc. In theillustrated example, a voicemail account status notificationcommunicated in the IVR audio segment 110 may be, for example,information notifying a user of a state of the user's voicemail accountsuch as quantities of new messages or saved messages and/or remainingstorage space. In the illustrated example, a confirmation communicatedin the IVR audio segment 110 may be an automated confirmatory voiceresponse indicating that a user's requested operation has been performedsuch as ‘message has been deleted’, ‘message has been saved’, ‘messagehas been forwarded’, ‘message has been sent’, ‘message has beenskipped’, ‘begin speaking to create a message’, etc.

The user input audio segment 112 of the illustrated example is used tocommunicate instructions, commands, codes or other informationcorresponding to operations specified by a user. Such information may bein the form of dual-tone multi-frequency (DTMF) signaling tones (e.g.,touch tones) corresponding to hard keys or soft keys pressed or selectedby a user. Additionally or alternatively, such information may be sentin the form of alphanumeric codes or symbols coded, modulated, orotherwise embedded in the user input audio segment 112.

In the illustrated example, the user device 102 and the IVR voicemailsystem 104 use error prevention and correction techniques to reduce orprevent instances of erroneous information from being displayed on theuser device 102 and/or reduce or prevent instances of unintendedoperations from being performed on messages in the IVR voicemail system104. Such error prevention and correction techniques may be any suitabletechnique(s) including, for example, forward error correction, hashsequencing, checksum transmissions, ack/nack (i.e.,acknowledge/negative-acknowledge) transmissions, etc.

In the illustrated example, the user device 102 includes a visualnotification and user input display area 114. The visual notificationand user input area 114 of the illustrated example displays informationelements such as graphics or text corresponding to information detectedin the IVR audio segment 110. For example, the user device 102 maydisplay visual cues such as user interface input/control prompts (e.g.,a delete message control, a save message control, a forward messagecontrol, a send message control, a skip message control, etc.) and/ornotifications such as confirmations of completed user requests (e.g.,confirmations of deleted messages, saved messages, forwarded messages,sent messages, skipped messages, etc.) and voicemail account statusinformation (e.g., a quantity of new messages, a quantity of savedmessages, a quantity of storage space remaining, etc.). Thus, the userdevice 102 may use the visual notification and user input area 114 ofthe illustrated example to display user input controls for selection byusers to request the IVR voicemail system 104 to perform desiredoperations (e.g., delete a message, save a message, forward a message,send a message, skip a message, etc.) as shown in the illustratedexample of FIG. 2 or to display information for viewing by a user asshown in the illustrated example of FIG. 3.

Turning to the illustrated example of FIG. 2, the example user device102 displays user control prompts 202 a-d (e.g., user-selectablegraphical icons or buttons) in the visual notification and user inputarea 114 based on information received from the IVR voicemail system 104via the IVR audio segment 110 of FIG. 1. The user control prompts 202a-d of the illustrated example are display elements or displayinformation that include a delete input control 202 a, a save inputcontrol 202 b, a skip input control 202 c, and a forward input control202 d. In other examples, other input controls may additionally oralternatively be displayed. In the illustrated example, when a userselects one or more of the user control prompts 202 a-d, the user device102 sends corresponding information (e.g., an instruction, a command, acode or other information corresponding to an operation specified by theuser) to the IVR voicemail system 104 via the user input audio segment112 of FIG. 1.

The illustrated example of FIG. 3 depicts the example user device 102displaying a visual notification 302 in the IVR audio segment 110 ofFIG. 1 based on information received from the IVR voicemail system 104.In the illustrated example, the visual notification 302 is aconfirmation notification (‘This message has been deleted’) confirmingthat a message has been deleted. The visual notification 302 is adisplay element or display information that informs a user via a visualinterface that the user's requested operation of deleting a message hasbeen successfully completed. Displaying of the visual notification 302of the illustrated example allows a user to observe a display (e.g., anexample display 810 of FIG. 8) of the user device 102 without needing tomove the user device 102 to his/her ear and determine whether aparticular message has been deleted based on such visual observation.

In the illustrated example of FIG. 3, the user device 102 also displaysdisplay elements or display information including an end control 304 aand a next control 304 b adjacent the visual notification 302. The endcontrol 304 a of the illustrated example enables a user to select to endthe voicemail call session 100 of FIG. 1. The next control 304 b of theillustrated example enables the user to hear a next voicemail message.In the illustrated example, the user device 102 may display the usercontrol prompts 304 a-b based on information communicated in the IVRaudio segment 110. Additionally or alternatively, the user device 102may be configured to always or automatically display the end control 304a and the next control 304 b when it detects receipt of information inthe IVR audio segment 110 confirming that a message has been deleted.

FIGS. 4-6 depict audio segments 400, 500, and 600 carrying informationusing different types of example techniques for detecting by the userdevice 102 of FIGS. 1-3 to display corresponding information in thevisual notification and user input area 114 of FIGS. 1-3. In theillustrated examples, each of the audio segments 400, 500, and 600 maybe used to implement the IVR audio segment 110 of FIG. 1. For example,some IVR voicemail systems and user devices employing example techniquesdisclosed herein may use a single type of the information conveyingtechniques shown in one of FIGS. 4-6 or a combination of different typesof the information conveying techniques of FIGS. 4-6. Although threeexample techniques for transmitting information to trigger or causevisual displays in the visual notification and user input area 114 aredisclosed, examples disclosed herein may be implemented in connectionwith other types of information transmission techniques alone or incombination with one or more of the example techniques of FIGS. 4-6 orany other suitable technique(s). Some such other types of informationtransmission techniques may involve establishing a data connectionconcurrently with a voice connection between the user device 102 and theIVR voicemail system 104 during the call session connection 106 of FIG.1 so that the IVR voicemail system 104 may communicate information tothe user device 102 via the data connection and send voice informationto the user device 102 via the voice connection.

FIG. 4 depicts an example audio segment 400 transmitting a voice portion402 (e.g., human-perceptible speech) on which the user device 102 mayperform speech recognition. For example, the user device 102 inaccordance with examples disclosed herein may be provided with speechrecognition and text-to-speech conversion capabilities to recognizevoiced information (e.g., the voice portion 402) that is otherwiseintended to be heard by a user of the user device 102 during a voicemailcall session (e.g., the voicemail call session 100 of FIG. 1). In suchinstances, the example user device 102 performs speech recognition onautomated voice-recorded portions or segments (e.g., the voice-recordedportion 402) sent by the IVR voicemail system 104 and displaysinformation in the visual notification and user input area 114 based onthe speech-recognized voice portion 402.

In the illustrated example of FIG. 4, in response to recognizing avoiced sentence that starts with ‘This message has been,’ the userdevice 102 recognizes that the voice portion 402 is a confirmation thata particular user-selected operation has been successfully performed. Inthe illustrated example, the user device 102 displays a correspondingconfirmation message in the visual notification and user input area 114based on a recognized keyword following the start of the sentence. Suchkeywords may be, for example, ‘deleted’ to indicate that a messagedelete operation has been successfully performed, ‘sent’ to indicatethat a message send operation has been successfully performed,‘forwarded’ to indicate that a message forward operation has beensuccessfully performed, and ‘saved’ to indicate that a message saveoperation has been successfully performed. For example, the user device102 may use a speech-recognition capability to convert some or all ofthe voice portion 402 to text format and display the recognized voiceportion 402 in text format. Additionally or alternatively, the userdevice 102 can access a database or look-up table locally stored thereinto retrieve a pre-defined graphic, user input control, or text stringcorresponding to the recognized voice portion 402 and display thepre-defined graphic or text string in the visual notification and userinput area 114.

FIG. 5 depicts an example audio segment 500 having a human-perceptibleaudio portion 502 and a human-imperceptible affixed information portion504. In the illustrated example, the human-perceptible audio portion 502is voiced information that is intended to be heard by a user of the userdevice 102 during a voicemail call session (e.g., the voicemail callsession 100 of FIG. 1). In the illustrated example of FIG. 5, thehuman-imperceptible affixed information portion 504 is information thatcorresponds to the human-perceptible audio portion 502. For example, ifthe human-perceptible audio portion 502 is a confirmation stating that amessage has been deleted, the human-imperceptible affixed informationportion 504 includes information corresponding to a deleted messageconfirmation that causes the user device 102 to display text and/orgraphic information in the visual notification and user input area 114confirming that a message has been deleted.

To generate the human-imperceptible affixed information portion 504, theIVR voicemail system 104 bursts information (e.g., tones, text, codes,symbols, etc.) adjacent to the human-perceptible audio portion 502 andmodulates the human-imperceptible affixed information 504 fortransmission over voice communications in a manner that prevents orminimizes its detectability or perceptibility by a user. In theillustrated example, by sending the human-imperceptible affixedinformation portion 504 as a suffix or post-fix following thehuman-perceptible audio portion 502, the human ear and/or brain is lesslikely to detect the presence of the human-imperceptible affixedinformation portion 504 and/or it is easier for the human ear and/orbrain to dismiss the human-imperceptible affixed information portion 504as non-intrusive or non-distracting static, noise, or other sound.Additionally or alternatively, the human-perceptible affixed information504 may be affixed to the beginning (e.g., pre-fixed information), themiddle (e.g., infixed information), the beginning and end (e.g.,circumfixed information), and/or interleaved through one or moreportions (e.g., transfixed information) of the human-perceptible audioportion 502.

Although the human-imperceptible affixed information 504 is shown in theillustrated example of FIG. 5 as affixed immediately adjacent to thehuman-perceptible audio 502, in other examples, the human-imperceptibleaffixed information 504 may be separated from the human-perceptibleaudio 502 by intervening silence or other audio or information (e.g.,human-perceptible and/or human-imperceptible audio or information). Insome examples, the human-imperceptible affixed information 504 istransmitted in another audio segment subsequent to or preceding theexample audio segment 500.

For examples in which the IVR audio segment 110 of FIG. 1 is implementedusing the example audio segment 500 of FIG. 5, the user device 102 isprovided with detection capabilities to detect information in thehuman-imperceptible affixed information portion 504 that causes the userdevice 102 to display corresponding information (e.g., graphics and/ortext) in the visual notification and user input area 114 of FIGS. 1-3.For example, the detection capabilities may enable the user device 102to detect information encoded by the IVR voicemail system 104 of FIG. 1in the human-imperceptible affixed information portion 504 at relativelylower power or volume levels than the human-perceptible audio portion502 and/or at one or more different frequencies (e.g., sidebandfrequencies) relative to the human-perceptible audio portion 502.

FIG. 6 depicts an example audio segment 600 having a human-perceptibleaudio portion 602 and human-imperceptible embedded information 604. Inthe illustrated example, the human-perceptible audio portion 602 isvoiced information that is intended to be heard by a user of the userdevice 102 during a voicemail call session (e.g., the voicemail callsession 100 of FIG. 1). In the illustrated example of FIG. 6, thehuman-imperceptible embedded information 604 is information thatcorresponds to the human-perceptible audio portion 602. For example, ifthe human-perceptible audio portion 602 is a confirmation stating that amessage has been deleted, the human-imperceptible embedded information604 includes information corresponding to a deleted message confirmationthat causes the user device 102 to display text and/or graphicinformation in the visual notification and user input area 114confirming that a message has been deleted.

To generate the human-imperceptible embedded information 604, the IVRvoicemail system 104 embeds, encodes, or otherwise inserts information(e.g., tones, text, codes, symbols, etc.) in the human-perceptible audioportion 602 and modulates the human-imperceptible embedded information604 for transmission over voice communications in a manner that preventsor minimizes its detectability or perceptibility by a user. In theillustrated example, by embedding, encoding, or otherwise inserting thehuman-imperceptible embedded information 604 in the audio segment 600,the human ear and/or brain is less likely to detect the presence of thehuman-imperceptible embedded information 604 and/or it is easier for thehuman ear and/or brain to dismiss the human-imperceptible information604 as non-intrusive or non-distracting static, noise, or other sound.For examples in which the IVR audio segment 110 of FIG. 1 is implementedusing the example audio segment 600 of FIG. 6, the user device 102 isprovided with detection capabilities to detect the human-imperceptibleembedded information 604 that causes the user device 102 to displaycorresponding information (e.g., graphics and/or text) in the visualnotification and user input area 114 of FIGS. 1-3.

FIG. 7 depicts an example apparatus 700 that may be used to implementthe example user device 102 of FIGS. 1-3. In the illustrated example ofFIG. 7, the apparatus 700 is provided with a processor 702, a user inputinterface 704, a display interface 706, a feature analyzer 708, acomparator 710, a memory 712, and a communication interface 714. Theprocessor 702, the user input interface 704, the display interface 706,the feature analyzer 708, the comparator 710, the memory 712, and/or thecommunication interface 714 may be implemented using any desiredcombination of hardware, firmware, and/or software. For example, one ormore integrated circuits, discrete semiconductor components, and/orpassive electronic components may be used. Thus, for example, theprocessor 702, the user input interface 704, the display interface 706,the feature analyzer 708, the comparator 710, the memory 712, and/or thecommunication interface 714, or parts thereof, could be implementedusing one or more circuit(s), programmable processor(s), applicationspecific integrated circuit(s) (ASIC(s)), programmable logic device(s)(PLD(s)), field programmable logic device(s) (FPLD(s)), etc. Theprocessor 702, the user input interface 704, the display interface 706,the feature analyzer 708, the comparator 710, the memory 712, and/or thecommunication interface 714, or parts thereof, may be implemented usinginstructions, code, and/or other software and/or firmware, etc. storedon a machine-accessible medium or computer-readable medium (e.g., thememory 712 of FIG. 7 and/or a memory 808 of FIG. 8) and executable by,for example, a processor (e.g., the example processor 702 of FIG. 7and/or a processor 802 of FIG. 8). When any of the appended claims areread to cover a purely software implementation, at least one of theprocessor 702, the user input interface 704, the display interface 706,the feature analyzer 708, the comparator 710, the memory 712, or thecommunication interface 714 is hereby expressly defined to include atangible medium such as a solid state memory, a magnetic memory, adigital versatile disk (DVD), a compact disk (CD), etc.

Turning in detail to FIG. 7, the apparatus 700 of the illustratedexample is provided with the example processor 702 to control and/ormanage operations of the user device 102 of FIGS. 1-3. In theillustrated example, the processor 702 receives information from one ormore of the user input interface 704, the feature analyzer 708, thecomparator 710, the memory 712, and/or the communication interface 714and makes decisions and facilitates information exchange internal andexternal to the user device 102.

To receive user input, the apparatus 700 is provided with the exampleuser input interface 704. In the illustrated example, the user inputinterface 704 is to be connected to one or more input devices (e.g., akeyboard 816, a touchscreen, and/or a microphone 820 of FIG. 8) toenable interactivity between a user and the user device 102. To displayinformation or display elements, the apparatus is provided with theexample display interface 706. In the illustrated example, the displayinterface 706 is to be connected to a display such as an example display810 of FIG. 8.

To analyze audio segments (e.g., one or more of the audio segments 110,400, 500, and/or 600 of FIGS. 1 and 4-6), the example apparatus 700 isprovided with the example feature analyzer 708. The feature analyzer 708of the illustrated example analyzes audio segments to detect andrecognize information located therein. For example, if the IVR audiosegment 110 of FIG. 1 is implemented using the audio segment 400 of FIG.4, the feature analyzer 708 is provided with speech recognitioncapabilities. For examples in which the IVR audio segment 110 of FIG. 1is implemented using the audio segment 500 of FIG. 5, the featureanalyzer 708 is provided with capabilities to detect affixed informationsuch as the human-imperceptible affixed information 504 of FIG. 5. Forexamples in which the IVR audio segment 110 of FIG. 1 is implementedusing the audio segment 600 of FIG. 6, the feature analyzer 708 isprovided with capabilities to detect information embedded, encoded, orotherwise inserted into human-perceptible audio such as thehuman-imperceptible embedded information 604 embedded in thehuman-perceptible audio 602.

In some examples, the feature analyzer 708 may be provided with acombination of different types of capabilities suitable to enable theuser device 102 to detect information in accordance with the techniquesdisclosed in any of FIGS. 4-6. In other examples that employ othertechniques for transmitting information to the user device 102 insteadof or in addition to any one or more of the techniques of FIGS. 4-6, thefeature analyzer 708 may be provided with capabilities to detectinformation in audio segments using any such other techniques. Forexample, some such other techniques may involve establishing a dataconnection concurrently with a voice connection between the user device102 and the IVR voicemail system 104 during the call session connection106 of FIG. 1. In such examples, the feature analyzer 708 can beconfigured to monitor information received on the data connection. Suchinformation is similar or identical to the information described asbeing transmitted in the human-imperceptible affixed information 504 ofFIG. 5 and/or the human-imperceptible embedded information 604 of FIG.6.

To compare information, the apparatus 700 is provided with the examplecomparator 710. For example, the user device 102 may locally storereference features (e.g., tonal frequency values, text, codes, symbols,etc.) to compare with information retrieved from features (e.g., thespeech of FIG. 4, the human-imperceptible affixed information portion504 of FIG. 5, the human-imperceptible embedded information 604 of FIG.6) detected in audio segments (e.g., one or more of the audio segments110, 400, 500, and/or 600 of FIGS. 1 and 4-6) to determine whether thedetected features correspond to information that the user device 102should display in the visual notification and user input area 114 ofFIGS. 1-3.

To store data and/or machine-readable or computer-readable instructions,the apparatus 700 is provided with the example memory 712. The memory712 of the illustrated example is implemented using the memory 808 ofFIG. 8. However, in other examples, the memory 712 may be implementedusing any other solid state, magnetic, or optical memory. In theillustrated example, the memory 712 is shown as storing a user controlslibrary or data structure 716 and a notifications library or datastructure 718. The user controls library 716 of the illustrated examplestores graphical user interface controls (e.g., the user control prompts202 a-d of FIG. 2 and/or 304 a-b of FIG. 3) for displaying in the visualnotification and user input area 114. The notifications library 718 ofthe illustrated example stores pre-defined notifications such asconfirmation messages (e.g., the visual notification 302 of FIG. 3) orvoicemail account status indications for displaying in the visualnotification and user input area 114. In the illustrated example,libraries 716 and 718 also store feature references in association withcorresponding user controls or pre-defined notifications stored therein.In this manner, the comparator 710 can compare features detected inaudio segments (e.g., one or more of the audio segments 110, 400, 500,and/or 600 of FIGS. 1 and 4-6) with feature references in the libraries716 and 718 to determine which stored user control(s) and/ornotification(s) should be displayed in the visual notification and userinput area 114.

In some examples, user controls stored in the user controls library 716and pre-defined notifications stored in the notifications library 718may be selected or specified by telecommunications carriers or operatorsthat provide subscriber services for user devices (e.g., the user device102 of FIGS. 1-3). Additionally or alternatively, the user controls andpre-defined notifications stored in the libraries 716 and 718 may beselected or specified by device manufacturers that manufacture such userdevices.

To exchange information or communicate with the IVR voicemail system 104of FIG. 1, the apparatus 700 is provided with the communicationinterface 714. In the illustrated example, the communication interface714 enables telephony communications via wired and/or wirelesscommunication media. In some examples, the communication interface 714also enables receiving and sending data via data channels. Thecommunication interface 714 of the illustrated example may beimplemented using any suitable type of telecommunication interface toenable establishing the call session connection 106 of FIG. 1. Suchexample telecommunication interfaces may include a POTS interface, awireless cellular interface, a VoIP interface, a public switchedtelephone network (PSTN) interface, a public land mobile network (PLMN)interface, and/or any other type of interface, and/or any combinationthereof.

FIG. 8 depicts a block diagram of an example implementation of aprocessor system that may be used to implement a mobile device such asthe user device 102 of FIGS. 1-3. In the illustrated example, the userdevice 102 is a two-way communication device with advanced datacommunication capabilities including the capability to communicate withother wireless-enabled devices or computer systems through a network oftransceiver stations. In the illustrated example, the user device 102also has the capability to allow voice communication. Depending on thefunctionality provided by the user device 102, it may be referred to asa data messaging device, a two-way pager, a cellular telephone with datamessaging capabilities, a smart phone, a wireless Internet appliance,and/or a data communication device (with or without telephonycapabilities). To aid the reader in understanding the structure of theuser device 102 and how it communicates with other devices and hostsystems, FIG. 8 will now be described in detail.

Referring to FIG. 8, the user device 102 includes a number of componentssuch as a main processor 802 that controls the overall operation of theuser device 102. Communication functions, including data and voicecommunications, are performed through a communication subsystem 804. Thecommunication subsystem 804 receives messages from and sends messages toa wireless network 805. In the illustrated example of the user device102, the communication subsystem 804 is configured in accordance withthe Global System for Mobile Communication (GSM) and General PacketRadio Services (GPRS) standards. The GSM/GPRS wireless network is usedworldwide and it is expected that these standards will be supersededeventually by Enhanced Data GSM Environment (EDGE) and Universal MobileTelecommunications Service (UMTS). New standards are still beingdefined, but it is believed that they will have similarities to thenetwork behavior described herein, and it will also be understood bypersons skilled in the art that the example implementations describedherein are intended to use any other suitable standards that aredeveloped in the future. The wireless link connecting the communicationsubsystem 804 with the wireless network 805 represents one or moredifferent Radio Frequency (RF) channels, operating according to definedprotocols specified for GSM/GPRS communications. With newer networkprotocols, these channels are capable of supporting both circuitswitched voice communications and packet switched data communications.

Although the wireless network 805 associated with the user device 102 isa GSM/GPRS wireless network in one example implementation, otherwireless networks may also be associated with the user device 102 invariant implementations. The different types of wireless networks thatmay be employed include, for example, data-centric wireless networks,voice-centric wireless networks, and dual-mode networks that can supportboth voice and data communications over the same physical base stations.Combined dual-mode networks include, but are not limited to, CodeDivision Multiple Access (CDMA) or CDMA2000 networks, GSM/GPRS networks(as mentioned above), and future third-generation (3G) networks likeEDGE and UMTS. Some other examples of data-centric networks include WiFi802.11, MOBITEX® and DATATAC® network communication systems. Examples ofother voice-centric data networks include Personal Communication Systems(PCS) networks like GSM and Time Division Multiple Access (TDMA)systems.

The main processor 802 also interacts with additional subsystems such asa Random Access Memory (RAM) 806, the persistent memory 808 (e.g., anon-volatile memory), the display 810, an auxiliary input/output (I/O)subsystem 812, a data port 814, the keyboard 816, a speaker 818, themicrophone 820, short-range communications 822, and other devicesubsystems 824.

Some of the subsystems of the user device 102 performcommunication-related functions, whereas other subsystems may provide“resident” or on-device functions. By way of example, the display 810and the keyboard 816 may be used for both communication-relatedfunctions, such as entering a text message for transmission over thenetwork 805, and device-resident functions such as a calculator or tasklist.

The user device 102 can send and receive communication signals over thewireless network 805 after required network registration or activationprocedures have been completed. Network access is associated with asubscriber or user of the user device 102. To identify a subscriber, theuser device 102 allows a SIM/RUIM card 826 (i.e., Subscriber IdentityModule or a Removable User Identity Module) to be inserted into aSIM/RUIM interface 828 to communicate with a network. The SIM card orRUIM 826 is one type of a conventional “smart card” that can be used toidentify a subscriber of the user device 102 and to personalize the userdevice 102, among other things. In some examples, without the SIM card826, the user device 102 is not fully operational for communication withthe wireless network 805. By inserting the SIM card/RUIM 826 into theSIM/RUIM interface 828, a subscriber can access all subscribed services.Services may include: web browsing and messaging such as e-mail, voicemail, Short Message Service (SMS), and Multimedia Messaging Services(MMS). More advanced services may include: point of sale, field serviceand sales force automation. The SIM card/RUIM 826 includes a processorand memory for storing information. Once the SIM card/RUIM 826 isinserted into the SIM/RUIM interface 828, it is coupled to the mainprocessor 802. In order to identify the subscriber, the SIM card/RUIM826 can include some user parameters such as an International MobileSubscriber Identity (I MSI). An advantage of using the SIM card/RUIM 826is that a subscriber is not necessarily bound by any single physicalmobile device. The SIM card/RUIM 826 may store additional subscriberinformation for a mobile device as well, including datebook (orcalendar) information and recent call information. Alternatively, useridentification information can also be programmed into the persistentmemory 808.

The user device 102 is a battery-powered device and includes a batteryinterface 832 for receiving one or more rechargeable batteries 830,which may be replaceable or non-replaceable. In at least someembodiments, the battery 830 can be a smart battery with an embeddedmicroprocessor. The battery interface 832 is coupled to a regulator (notshown), which assists the battery 830 in providing power V+ to the userdevice 102. Although current technology makes use of a battery, futuretechnologies such as micro fuel cells, solar cells, etc. may provide thepower to the user device 102.

The user device 102 also includes an operating system 834 and softwarecomponents 836 to 846 which are described in more detail below. Theoperating system 834 and the software components 836 to 846 that areexecuted by the main processor 802 are typically stored in a persistentstore such as the persistent memory 808, which may alternatively be aread-only memory (ROM) or similar storage element (not shown). Thoseskilled in the art will appreciate that portions of the operating system834 and the software components 836 to 846, such as specific deviceapplications, or parts thereof, may be temporarily loaded into avolatile store such as the RAM 806. Other software components can alsobe included, as is well known to those skilled in the art.

The subset of software applications 836 that control basic deviceoperations, including data and voice communication applications, willnormally be installed on the user device 102 during its manufacture.Other software applications include a message application 838 that canbe any suitable software program that allows a user of the user device102 to send and receive electronic messages. Various alternatives existfor the message application 838 as is well known to those skilled in theart. Messages that have been sent or received by the user are typicallystored in the persistent memory 808 of the user device 102 or some othersuitable storage element in the user device 102. In at least someembodiments, some of the sent and received messages may be storedremotely from the user device 102 such as in a data store of anassociated host system with which the user device 102 communicates.

The software applications can further include a device state module 840,a Personal Information Manager (PIM) 842, and other suitable modules(not shown). The device state module 840 provides persistence (i.e., thedevice state module 840 ensures that important device data is stored inpersistent memory, such as the persistent memory 808, so that the datais not lost when the user device 102 is turned off or loses power).

The PIM 842 includes functionality for organizing and managing dataitems of interest to the user, such as, but not limited to, e-mail,contacts, calendar events, voice mails, appointments, and task items. APIM application has the ability to send and receive data items via thewireless network 805. PIM data items may be seamlessly integrated,synchronized, and updated via the wireless network 805 with the mobiledevice subscriber's corresponding data items stored and/or associatedwith a host computer system. This functionality creates a mirrored hostcomputer on the user device 102 with respect to such items. This can beparticularly advantageous when the host computer system is the mobiledevice subscriber's office computer system.

The user device 102 also includes a connect module 844, and an IT policymodule 846. The connect module 844 implements the communicationprotocols used by the mobile device 108 to communicate with the wirelessinfrastructure and any host system, such as an enterprise system, withwhich the user device 102 is authorized to interface.

The connect module 844 includes a set of APIs that can be integratedwith the user device 102 to allow the user device 102 to use any numberof services associated with the enterprise system. The connect module844 allows the user device 102 to establish an end-to-end secure,authenticated communication pipe with the host system. A subset ofapplications for which access is provided by the connect module 844 canbe used to pass IT policy commands from the host system (e.g., from anIT policy server of a host system) to the user device 102. This can bedone in a wireless or wired manner. These instructions can then bepassed to the IT policy module 846 to modify the configuration of themobile device 102. Alternatively, in some cases, the IT policy updatecan also be done over a wired connection. The IT policy module 846receives IT policy data that encodes the IT policy. The IT policy module846 then ensures that the IT policy data is authenticated by the userdevice 102. The IT policy data can then be stored in the flash memory806 in its native form.

Other types of software applications can also be installed on the userdevice 102. These software applications can be third party applications,which are added after the manufacture of the user device 102. Examplesof third party applications include games, calculators, utilities, etc.

The additional applications can be loaded onto the user device 102through at least one of the wireless network 805, the auxiliary I/Osubsystem 812, the data port 814, the short-range communicationssubsystem 822, or any other suitable device subsystem 824. Thisflexibility in application installation increases the functionality ofthe user device 102 and may provide enhanced on-device functions,communication-related functions, or both. For example, securecommunication applications may enable electronic commerce functions andother such financial transactions to be performed using the user device102.

The data port 814 enables a subscriber to set preferences through anexternal device or software application and extends the capabilities ofthe user device 102 by providing for information or software downloadsto the user device 102 other than through a wireless communicationnetwork. The alternate download path may, for example, be used to loadan encryption key onto the user device 102 through a direct and thusreliable and trusted connection to provide secure device communication.

The data port 814 can be any suitable port that enables datacommunication between the user device 102 and another computing device.The data port 814 can be a serial or a parallel port. In some instances,the data port 814 can be a USB port that includes data lines for datatransfer and a supply line that can provide a charging current to chargethe battery 830 of the user device 102.

The short-range communications subsystem 822 provides for communicationbetween the user device 102 and different systems or devices, withoutthe use of the wireless network 805. For example, the subsystem 822 mayinclude an infrared device and associated circuits and components forshort-range communication. Examples of short-range communicationstandards include standards developed by the Infrared Data Association(IrDA), a Bluetooth® communication standard, and the 802.11 family ofstandards developed by IEEE.

In use, a received signal such as a text message, an e-mail message, aweb page download, media content, etc. will be processed by thecommunication subsystem 804 and input to the main processor 802. Themain processor 802 will then process the received signal for output tothe display 810 or alternatively to the auxiliary I/O subsystem 812. Asubscriber may also compose data items, such as e-mail messages, forexample, using the keyboard 816 in conjunction with the display 810 andpossibly the auxiliary I/O subsystem 812. The auxiliary subsystem 812may include devices such as: a touch screen, mouse, track ball, infraredfingerprint detector, or a roller wheel with dynamic button pressingcapability. The keyboard 816 is preferably an alphanumeric keyboardand/or telephone-type keypad, and may be either a physical keyboard or atouch screen keyboard. However, other types of keyboards may also beused. A composed item may be transmitted over the wireless network 805through the communication subsystem 804.

For voice communications, the overall operation of the user device 102is substantially similar, except that the received signals are output tothe speaker 818, and signals for transmission are generated by themicrophone 820. Alternative voice or audio I/O subsystems, such as avoice message recording subsystem, can also be implemented on the userdevice 102. Although voice or audio signal output is accomplishedprimarily through the speaker 818, the display 810 can also be used toprovide additional information such as the identity of a calling party,duration of a voice call, or other voice call related information.

FIGS. 9-12 depict example flow diagrams representative of processes thatmay be implemented using, for example, computer-readable instructionsstored on a computer-readable medium to facilitate voicemailinteractions based on detecting features in transmissions from the IVRvoicemail system 104 of FIG. 1. The example processes of FIGS. 9-12 maybe performed using one or more processors, controllers, and/or any othersuitable processing devices. For example, the example processes of FIG.9-12 may be implemented using coded instructions (e.g., computerreadable instructions) stored on one or more tangible computer readablemedia such as flash memory, read-only memory (ROM), and/or random-accessmemory (RAM). As used herein, the term tangible computer readable mediumis expressly defined to include any type of computer readable storageand to exclude propagating signals. Additionally or alternatively, theexample processes of FIGS. 9-12 may be implemented using codedinstructions (e.g., computer-readable instructions or machine-accessibleinstructions) stored on one or more non-transitory computer readablemedia such as flash memory, read-only memory (ROM), random-access memory(RAM), cache, or any other storage media in which information is storedfor any duration (e.g., for extended time periods, permanently, briefinstances, for temporarily buffering, and/or for caching of theinformation). As used herein, the term non-transitory computer-readablemedium and non-transitory machine-accessible medium are expresslydefined to include any type of computer-readable medium ormachine-accessible medium and to exclude propagating signals.

Alternatively, some or all operations of the example processes of FIGS.9-12 may be implemented using any combination(s) of application specificintegrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)),field programmable logic device(s) (FPLD(s)), discrete logic, hardware,firmware, etc. Also, some or all operations of the example processes ofFIGS. 9-12 may be implemented manually or as any combination(s) of anyof the foregoing techniques, for example, any combination of firmware,software, discrete logic and/or hardware. Further, although the exampleprocesses of FIGS. 9-12 are described with reference to the flowdiagrams of FIGS. 9-12, other methods of implementing the processes ofFIGS. 9-12 may be employed. For example, the order of execution of theblocks may be changed, and/or some of the blocks described may bechanged, eliminated, sub-divided, or combined. Additionally, any or alloperations of the example processes of FIGS. 9-12 may be performedsequentially and/or in parallel by, for example, separate processingthreads, processors, devices, discrete logic, circuits, etc.

In the illustrated example, the processes of FIGS. 9-12 are describedbelow as performed by the user device 102 of FIGS. 1-3 as implementedusing the example apparatus 700 of FIG. 7. However, the exampleprocesses of FIGS. 9-12 may additionally or alternatively be implementedusing any other suitable device or apparatus.

Now turning in detail to FIG. 9, initially, the communication interface714 (FIG. 7) establishes the voicemail call session connection 100 ofFIG. 1 (block 902). The communication interface 714 determines whetherit has received an audio segment (e.g., the IVR audio segment 110 ofFIG. 1) (block 904). If the communication interface 714 has not receivedan audio segment, control remains at block 904 until an audio segmenthas been received. Otherwise, if the communication interface 714 hasreceived the IVR audio segment 110, the feature analyzer 708 (FIG. 7)analyzes the IVR audio segment 110 (block 906) and determines whether ithas detected a feature in the IVR audio segment 110 (block 908). In someexamples, the feature is recognizable speech as discussed above inconnection with the audio segment 400 of FIG. 4. In other examples, thefeature is the human-imperceptible affixed information 504 of the audiosegment 500 of FIG. 5. In yet other examples, the feature is thehuman-imperceptible embedded information 604 of the audio segment 600 ofFIG. 6.

If the feature analyzer 708 does not detect a feature at block 908, theapparatus 700 ignores the audio segment (block 910), and control returnsto block 904 until another audio segment is received. If the featureanalyzer 708 does detect a feature at block 908, control advances toblock 912 at which the feature analyzer 708 processes the detectedfeature. Example processes that may be used to implement the operationof block 912 are described below in connection with FIGS. 10-12.

After the feature is processed at block 912, the comparator 710 (FIG. 7)determines whether the feature corresponds to a prompt for user input(block 914). For example, the comparator 710 can compare the feature (orinformation in the feature) with reference features stored in the usercontrols library 716 and the notifications library 718 of FIG. 7 todetermine a corresponding action for displaying information in thevisual notification and user input area 114. In this manner, if thecomparator 710 finds, at block 914, a user control and/or notificationcorresponding to a prompt for user input based on the detected feature,the display interface 706 (FIG. 7) retrieves the corresponding usercontrol and/or notification text/information and/or graphic displayelement(s) for display from the user controls library 716 and/or thenotifications library 718 (block 916). For example, a user-selectableuser control may be displayed to enable a user to select the usercontrol to request a particular operation and/or a notification may bedisplayed to inform a user of which keypad key to press to request aparticular operation. After retrieving the user control and/ornotification at block 916, control advances to block 922.

If the comparator 710 determines, at block 914, that the feature doesnot correspond to a prompt for user input, control advances to block 918at which the comparator 710 determines whether the feature correspondsto a notification (block 918). For example, the comparator 710 cancompare the feature (or information in the feature) with referencefeatures stored in the notifications library 718 of FIG. 7 to determinea corresponding action for displaying information in the visualnotification and user input area 114. If the comparator 710 determines,at block 918, that the detected feature does not correspond to anotification, control advances to block 926. However, if the comparator710 finds, at block 918, a notification corresponding to the detectedfeature, the display interface 706 (FIG. 7) retrieves the correspondingnotification text/information and/or graphic display element(s) fordisplay from the notifications library 718 (block 920).

In examples in which the feature is recognizable speech (e.g., asdiscussed above in connection with FIG. 4) that the user device 102converts into text format to display the converted text in the visualnotification and user input area 114, the operation of block 916 and/orthe operation of block 920 may be skipped. That is, in such examples thedisplay interface 706 displays the converted text in the visualnotification and user input area 114 instead of retrieving anddisplaying display elements or display information from the libraries716 and 718.

After the display interface 706 retrieves a user control and/or anotification text/information and/or graphic display element(s) at block916 or retrieves a notification text/information and/or graphic displayelement(s) at block 920, the display interface 706 generates a userinterface view (block 922) to present the retrieved display element(s)or display information. Example user interface views that may begenerated by the display interface 706 are shown in the visualnotification and user input area 114 of FIGS. 2 and 3. The displayinterface 706 then displays the user interface view (block 924) with thedisplay element(s) or display information in the visual notification anduser input area 114 (FIGS. 1-3) via, for example, the display 810 ofFIG. 8.

The processor 702 (FIG. 7) determines whether to continue monitoring thevoicemail call session 100 via the call session connection 106 of FIG. 1(block 926). For example, if the voicemail call session 100 has notended, control returns to block 904 to continue to monitor the voicemailcall session 100. Otherwise, if the voicemail call session 100 hasended, the processor 702 determines that the user device 102 is not tocontinue monitoring the voicemail call session 100 (block 926), and theexample process of FIG. 9 ends.

Although blocks 904, 906, 908, 910, and 912 are described above as beingperformed in connection with an audio segment (e.g., one of the IVRaudio segment 110 of FIG. 1 and/or the audio segments 400, 500, and 600of FIGS. 4-6), in other examples in which detectable feature informationis received at the user device 102 via data connections, operations ofthe blocks 904, 906, 908, 910, and 912 may be performed on data receivedat the user device 102 via data segments over the data connection ratherthan on audio segments received via an audio connection.

Turning now to FIG. 10, an illustrated example flow diagram isrepresentative of computer-readable instructions that may be used toperform speech recognition on audio segments (e.g., the audio segment110 of FIG. 1 and/or the audio segment 400 of FIG. 4) in connection withthe example flow diagram of FIG. 9. In the illustrated example, theexample process of FIG. 10 may be used to implement the operation ofblock 912 of FIG. 9 and is described in connection with the audiosegment 400 of FIG. 4. To process information in a detected feature(e.g., the feature detected at block 908 of FIG. 9) in accordance withthe example process of FIG. 10, the feature analyzer 708 (FIG. 7)performs a speech recognition process on a voice signal or voice portion(e.g., the detected feature) of the audio segment 400 of FIG. 4 (block1002). The feature analyzer 708 then performs a speech-to-textconversion based on the results of the speech recognition process (block1004). Control then returns to a calling function or process such as theexample process of FIG. 9, and the example process of FIG. 10 ends.

FIG. 11 depicts an example flow diagram representative ofcomputer-readable instructions that may be used to retrieve informationfrom human-imperceptible affixed signals (e.g., the human-imperceptibleaffixed information 504 of FIG. 5) in audio segments (e.g., the audiosegment 110 of FIG. 1 and/or the audio segment 500 of FIG. 5) inconnection with the example flow diagram of FIG. 9. In the illustratedexample, the example process of FIG. 11 may be used to implement theoperation of block 912 of FIG. 9 and is described in connection with theaudio segment 500 of FIG. 5. To process information in a detectedfeature (e.g., the feature detected at block 908 of FIG. 9) inaccordance with the example process of FIG. 11, the feature analyzer 708(FIG. 7) performs an affixed information detection process on the audiosegment 500 of FIG. 5 (block 1102) to detect the location of thehuman-imperceptible affixed information 504 in the audio segment 500.The feature analyzer 708 then retrieves the human-imperceptible affixedinformation 504 from the audio segment 500 (block 1104). Control thenreturns to a calling function or process such as the example process ofFIG. 9, and the example process of FIG. 11 ends.

FIG. 12 depicts an example flow diagram representative ofcomputer-readable instructions that may be used to retrieve embeddedinformation (e.g., the human-perceptible embedded information 604 ofFIG. 6) from audio segments (e.g., the audio segment 110 of FIG. 1and/or the audio segment 600 of FIG. 6) in connection with the exampleflow diagram of FIG. 9. In the illustrated example, the example processof FIG. 12 may be used to implement the operation of block 912 of FIG. 9and is described in connection with the audio segment 600 of FIG. 6. Toprocess information in a detected feature (e.g., the feature detected atblock 908 of FIG. 9) in accordance with the example process of FIG. 12,the feature analyzer 708 (FIG. 7) performs an embedded informationdetection process on the audio segment 600 of FIG. 6 (block 1202) todetect the location of the human-imperceptible embedded information 604in the audio segment 600. The feature analyzer 708 then retrieves thehuman-imperceptible embedded information 604 from the audio segment 600(block 1204). Control then returns to a calling function or process suchas the example process of FIG. 9, and the example process of FIG. 12ends.

In some examples disclosed herein, an example method to facilitatevoicemail interaction involves, during a call session with a voicemailsystem, receiving an audio segment from the voicemail system. Featurerecognition is performed on the audio segment. A display element isoutput to a user interface based on a recognized feature in the audiosegment. Such examples enable users to conduct voicemail systeminteractions using visual information displayed on a user device. Somedisclosed examples substantially reduce the need for repeated back andforth movement of a user device between a user's ear and the user'svisual space by reducing the number of times that the user must put theuser device to his/her ear to listen to audio prompts, move the userdevice away from his/her ear to press a key for a desired action (e.g.,delete, save, forward, send, skip, create, etc. a voicemail message),and move the user device back to his/her ear to listen for an audionotification or confirmation that the desired action has occurred. Suchback and forth movement between a user's ear and the user's view of theuser device may otherwise be time consuming, tedious, and cumbersomewhen navigating a voicemail call session. For example, such back andforth movement introduces discontinuities in a user's visual focus on auser device keypad or touch-screen display such that each time a usermoves the user device back into viewing position, the user must refocusand re-orient his/her sight on the user device keypad or touch-screendisplay. Similarly, each time the user moves the user device back tohis/her ear, the user must re-position the device for optimal comfortand hearing. As such, some examples disclosed herein advantageouslyimprove user experience during voicemail interaction by providingrelatively better continuity between a user providing input to avoicemail system and the user receiving feedback or confirmations fromthe voicemail system.

Some examples disclosed herein advantageously reduce the need for usersto rely solely on hearing and remembering audio information (e.g.,prompts, notifications, confirmations, etc.) during a voicemail callsession. In this manner, if a user is involved in a voicemail callsession while in a noisy environment, examples disclosed herein enablethe user to receive visual information (e.g., prompts, notifications,confirmations, etc.) that would otherwise be available only via audioinformation from the voicemail system. Such receipt of information in avisual manner may advantageously reduce or eliminate confusion andincrease user-understanding or clarity as to which keys to press fordifferent features or operations (e.g., delete, save, forward, send,skip, create, etc. a voicemail message). Such example advantages maysubstantially reduce or eliminate user-frustration and potentially riskyscenarios (e.g., initiating a delete operation when a save operation wasintended) that could otherwise occur using prior art voicemail systemsif a person incorrectly hears or mis-interprets received audioinformation.

Although certain methods, apparatus, and articles of manufacture havebeen disclosed herein, the scope of coverage of this patent is notlimited thereto. To the contrary, this patent covers all methods,apparatus, and articles of manufacture fairly falling within the scopeof the claims either literally or under the doctrine of equivalents.

What is claimed is:
 1. A method to facilitate voicemail interaction,comprising: during a call session with a voicemail system, receiving anaudio segment at a user device from the voicemail system; performingfeature recognition on the audio segment at the user device during thecall session by detecting human imperceptible information embedded inthe audio segment; and outputting a display element to a user interfaceof the user device during the call session based on a recognized featurein the audio segment, after a comparator determines that the displayelement corresponds to the audio segment.
 2. A method as defined inclaim 1, wherein performing the feature recognition comprises:performing speech recognition on a voice portion of the audio segment;and recognizing one or more words of the voice portion.
 3. A method asdefined in claim 1, wherein the display element is a user interfacecontrol to control the voicemail system to at least one of send amessage, skip a message, and delete a message.
 4. A method as defined inclaim 1, wherein the human-imperceptible information is at least one oftext and a code modulated for transmission over voice communications. 5.A method as defined in claim 1, wherein performing the featurerecognition comprises detecting human-imperceptible affixed informationthat is one of: affixed to a voice portion of the audio segment; andreceived in one of the audio segment and another audio segmentsubsequent to or preceding the audio segment.
 6. A method as defined inclaim 1, wherein the display element is one of a graphical userinterface control, a notification confirming completion of auser-requested operation, and a notification requesting user-initiationof a user-requested operation.
 7. A method as defined in claim 1,wherein the user device is a telephony-capable mobile device.
 8. Anapparatus to facilitate voicemail interaction, comprising: acommunication interface operable to, during a call session with avoicemail system, receive an audio segment from the voicemail system; afeature analyzer operable to perform feature recognition on the audiosegment by detecting human imperceptible information embedded in theaudio segment; a user interface having at least one user interfacecontrol; and a display interface operable to output the user interfacecontrol to the user interface based on a recognized feature in the audiosegment, after a comparator determines that the display elementcorresponds to the audio segment, the user interface control operable tocontrol the voicemail system.
 9. An apparatus as defined in claim 8,wherein the feature analyzer is operable to perform the featurerecognition by: performing speech recognition on a voice portion of theaudio segment; and recognizing one or more words of the voice portion.10. An apparatus as defined in claim 9, wherein the one or more wordscomprise at least one option to control the voicemail system, the atleast one option presented as the user interface control is operable toperform at least one of sending a message, skipping a message, ordeleting a message.
 11. An apparatus as defined in claim 9, wherein thehuman-imperceptible information is at least one of text and a codemodulated for transmission over voice communications.
 12. An apparatusas defined in claim 8, wherein the feature analyzer is operable toperform the feature recognition by detecting human-imperceptible affixedinformation that is one of: affixed to a voice portion of the audiosegment; and received in one of the audio segment and another audiosegment subsequent to or preceding the audio segment.
 13. An apparatusas defined in claim 8, wherein the information is one of a graphicaluser interface control and a notification confirming the completion of auser-requested operation.
 14. An apparatus as defined in claim 8,wherein the apparatus is a telephony-capable mobile device.
 15. Amachine-accessible storage medium having instructions stored thereonthat, when executed, cause a processor of a user device to at least:during a call session with a voicemail system, receive an audio segmentfrom the voicemail system; perform feature recognition on the audiosegment during the call session by detecting human imperceptibleinformation embedded in the audio segment; and output a display elementto a user interface of the user device during the call session based ona recognized feature in the audio segment, after a comparator determinesthat the display element corresponds to the audio segment.
 16. Amachine-accessible medium as defined in claim 15 having instructionsstored thereon that, when executed, cause the processor to perform thefeature recognition by: performing speech recognition on a voice portionof the audio segment; and recognizing one or more words of the voiceportion.
 17. A machine-accessible medium as defined in claim 15, whereinthe display element is one of a graphical user interface control, anotification confirming selection of a user-requested operation, and anotification confirming completion of a user-requested operation.